home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19971216-19980424
/
000124_news@newsmaster….columbia.edu _Mon Jan 26 21:56:45 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1998-04-22
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id VAA22906
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 26 Jan 1998 21:56:45 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id VAA14926
for kermit.misc@watsun; Mon, 26 Jan 1998 21:56:44 -0500 (EST)
Path: news.columbia.edu!panix!howland.erols.net!news-peer.sprintlink.net!news-peer-west.sprintlink.net!news.sprintlink.net!Sprint!news.sprintisp.com!sprintisp!not-for-mail
From: "David M. Venus" <dvenus@sprintmail.com>
Newsgroups: comp.protocols.kermit.misc
Subject: Exit status of external protocols - HELP !
Date: Tue, 27 Jan 1998 09:54:53 -0500
Lines: 27
Message-ID: <34CDF53D.6300@sprintmail.com>
Reply-To: dvenus@sprintmail.com
NNTP-Posting-Host: 168.191.67.26
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01C-SI300B01 (Win95; I)
Xref: news.columbia.edu comp.protocols.kermit.misc:8304
Hi !
I am using Kermit 6.0.192 on HP-UX 10.10 with external protocols.
Specifically I am using lrzsz with the Xmodem protocol (sx). When
the transfer fails I see the message: ?Command exited with status: 1.
I have determined this comes from the module ckvtio.c (? I think that is
the right one :-). However this value is not placed in \v(status)
variable. Right after the send I have an IF FAILURE forward LABEL
statement. Kermit ought to follow this branch because the transfer
failed but does not it executes the echo statment after that that says
the transfer was successful ! :-(
Is there a patch to fix this problem ? If not how can I code/script
around this problem ? I don't have a choice of using another protocol
:-(( as the system on the other end only supports "old" 128 byte record
Xmodem (not even Xmodem-1K !).
Please help ! Any suggestions will be gratefully accepted.
Please e-mail if possible to: dvenus@hotmail.com.
Thanks,
Dave Venus
SysAdmin/DBA
Metromont Materials
Spartanburg, SC.